home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-09-01 | 1.4 KB | 45 lines | [TEXT/GEOL] |
- Item 8884616 31-Aug-89 04:58
-
- From: SW0075 SWV VTS Transportation Systems, GBG
-
- To: MACAPP.TECH$ MACAPP Tech
-
- Sub: MacApp Memory management
-
- From : SW0075 VTS Transportation Systems, Sweden
-
- To : MACAPP.TECH$ MACAPP Tech
-
- Sub: MacApp Memory management
-
- Hi,
- We are using MacApp 2.0, MPW 3.0 and SADE 1.0 .
-
- In order to create a temporary nonrelocatable memory block without fragmenting
- the heap, we followed the recommendations in Inside Macintosh, vol. II, page
- 41.
-
- When the toolbox routine MoveHHi(handle) and HLock(handle) are called, the
- handle's memory block is moved directly above the last loaded code segment,
- see the SADE heap dump below.
-
- $002AA5E0 $000CD7FC F
- •$00377DE4 $00007534 H $00295DB4 L Saved bits under a menu
- •$0037F320 $00002488 H $00293AE8 LPR CODE 20 $0584 "ASegment"
-
- In our interpretation of the MacApp documentation, this memory block resides
- inside the temporary space as defined in MacApp. In subsequent processing, will
- this invalid memory block location cause a severe error when more segments are
- loaded ?
-
- Could you describe what is really happening in the case above, and how to
- handle this situation without letting the permanent and temporary memory space
- overlap.
-
-
- Bo Ridderstolpe
- Dan Ryrlén
- VTS
-
-
-